Deploying C++Builder Applications ----------------------------- Please read this file before deploying C++Builder applications, components, or libraries. This file is provided pursuant to the Borland No-Nonsense License Statement and provides information on deploying 1. The C++Builder application .EXE file (and any DLLs and BPLs the application requires). 2. Components and design-time packages. 3. The Borland Database Engine (BDE). 4. ActiveX controls (OCXs). 5. Sample Images. 6. Single-user InterBase and multi-user InterBase Server. 7. Multi-tiered Distributed Application Services (MIDAS). 8. SQL Links support for remote server access. 9. Removed or modified "Redistributable" files. It is recommended that you use InstallShield Express, or another Borland-certified install program, to deploy your applications. ======================================================================= 1. Application deployment (all applications) -------------------------------------------- If you build statically linked applications, C++Builder applications do not require a runtime interpreter DLL. All you have to provide is your .EXE file and any DLLs or BPLs it calls. If you build using the dynamic Run-Time Library, you will also have to distribute the Run-Time Library DLLs, BORLNDMM.DLL, and CP3240MT.DLL. If you use InstallShield, treat .BPL (package) files just like other DLLs. From the Setup Checklist, open Groups and Files, then click Add Group. You can create a group called "Packages" for BPLs; to install packages in the Windows\System directory, choose as the destination directory. (We recommend installing .DLL and .BPL files in the Windows\System directory.) Then click Launch Explorer to select the BPL files you want to deploy. NOTE: When you deploy applications that use the TCoolBar component, make sure that end-users have version 4.70 or later of COMCTL32.DLL. Setting the Flat property of TToolBar to True also requires version 4.70 or later of COMCTL32.DLL. For a list of other components that work best with the latest version of COMCTL32.DLL, see README.HLP. TREGSVR.EXE is fully redistributable. The internet controls by NetMasters are fully redistributable. 2. Components, design-time packages, and runtime packages --------------------------------------------------------- If you distribute C++Builder packages to other developers, be sure to supply the .BPL files, header files, the built package file (.BPL), dynamically linked packages .BPI) if used, and statically linked packages (.LIB) if used. In accordance with the General Terms That Apply to Compiled Programs and Redistributables, you may redistribute Borland-supplied runtime packages only for the purpose of executing application programs created with C++Builder. You may not modify these packages in any way. If you are a licensed user of C++Builder Enterprise or Client/Server, redistributable runtime packages include the following: BCBSMP35.BPL DSS35.BPL IBEVNT35.BPL INET35.BPL INETDB35.BPL NMFAST.BPL QRPT35.BPL TEE35.BPL TEEDB35.BPL TEEUI35.BPL VCL35.BPL VCLDB35.BPL VCLDBX35.BPL VCLSMP35.BPL VCLX35.BPL If you are a licensed user of C++Builder Professional, redistributable runtime packages include the following: BCBSMP35.BPL IBEVNT35.BPL INET35.BPL INETDB35.BPL NMFAST.BPL QRPT35.BPL TEE35.BPL TEEDB35.BPL TEEUI35.BPL VCL35.BPL VCLDB35.BPL VCLDBX35.BPL VCLSMP35.BPL VCLX35.BPL If you are a licensed user of C++Builder Standard, redistributable runtime packages include the following: BCBSMP35.BPL QRPT35.BPL VCL35.BPL VCLDB35.BPL VCLDBX35.BPL VCLSMP35.BPL VCLX35.BPL Although this software may include packages other than those listed above, only the packages listed above are redistributable. You may NOT redeploy Borland-supplied design-time-only packages. You may not recompile or redistribute any Borland-supplied components or libraries for use by other developers. Packages that you develop may not have the same names as Borland- supplied packages. Deploying applications that use packages ________________________________________ When distributing an application that uses runtime packages, make sure that your users have the application's .EXE file as well as all the library (.BPL or .DLL) files that the application calls. If the library files are in a different directory from the .EXE file, they must be accessible through the user's Path. You may want to follow the convention of putting library files in the Windows\System directory. If you use InstallShield Express, your installation script can check the user's system for any packages it requires before blindly reinstalling them. Distributing packages to other developers _________________________________________ If you distribute runtime or design-time packages to other C++Builder developers, be sure to supply both .BPI and .BPL files as well as any required header files. To link components statically into their applications that is, to build applications that do not use runtime packages -- developers will also need .LIB (or .OBJ) files for any packages you supply. 3. BDE deployment (all database applications) --------------------------------------------- Borland Database Engine (BDE) redistributable files --------------------------------------------------- In accordance with the Additional License Terms for Borland Database Engine (see LICENSE.TXT), you may distribute the Borland Database Engine files with your application using a Borland- certified Redistributable Install program such as InstallShield Express or another compliant install program. You may redistribute only those BDE files selected by the Borland-certified install program. C++Builder 3 includes InstallShield Express, a certified install program that facilitates proper installation and un-installation of C++Builder applications. InstallShield Express helps ensure that your applications co-exist well with other software that uses the BDE, such as dBASE, Paradox, and Delphi. InstallShield Express also makes it easy to distribute subsets of the Borland Database Engine; this is useful, for example, if you want to distribute an application that uses only dBASE tables, and you don't want to include additional files for Paradox support. NOTE: InstallShield Express installs the MS Access driver with the ODBC driver. To deploy Access applications, select the ODBC driver in InstallShield. The Access driver requires installation of the JET engine (DAO 3.0) on the computer where it is deployed. NOTE: Do not deploy DB-Lib and CT-Lib with the same application. DB-Lib is for Sybase 4.2 or lower, and CT-Lib is for Sybase System 10 and higher. From time to time, Borland may, at its discretion, certify additional installation programs for use as a Borland Certified Install Program for this product. You should visit Borland's Web site (http://www.borland.com/) for the latest information, including the current list (CERTINST.DOC) of Borland Certified Install programs (if any) for this product. Deployment of Borland Database Engine files and subsets must be done with a Borland Certified Install Program. We do not otherwise allow deployment of the individual BDE files. There are several important reasons for this: o Improper installation of the BDE or BDE subsets can cause other applications using the BDE to fail. Such applications include not only Borland products, but many other programs that use the BDE, such as those built with and C++Builder and Delphi. o Windows 95 and Windows NT use the registry instead of .INI files, and making the correct entries and deletions for install and un-install is also a complex task. By working closely with Borland Certified Install Program providers, we can ensure that all the installation, registry, and un-install tasks are handled correctly. 4. ActiveX controls (OCXs) -------------------------- C++Builder 3 includes ActiveX Controls (OCXs) for use in your applications: o Chart FX, copyright SoftwareFX Inc. o VisualSpeller Control, copyright Visual Components, Inc. o Formula One (spreadsheet), copyright Visual Components, Inc. o First Impression (VtChart), copyright Visual Components, Inc. o Graph Custom Control, copyright Bits Per Second Ltd. The version of each of these OCXs shipped with C++Builder may be redistributed in custom C++Builder applications. Such redistribution is subject to the General Terms That Apply to Compiled Programs and Redistributables. 5. Sample images ---------------- C++Builder 3 includes a library of redistributable bitmap images normally installed in the subdirectory: Program Files\Common Files\Borland Shared\IMAGES. C++Builder 3 also includes a database EVENTS.DB with licensed images from PhotoDisc. The images in this database are copyright PhotoDisc, Inc. 1995 and may not be redistributed. 6. Local InterBase and multi-user InterBase Server deployment ------------------------------------------------------------- Applications that use the 32-bit Local InterBase ------------------------------------------------ C++Builder Enterprise, Client/Server, and Professional editions include a development license for Local InterBase. They do not, however, include rights for deployment or redistribution of any InterBase component. To deploy InterBase applications, you must purchase Deployment Kits; contact Borland at 1-800-245-7367 for details. Applications that use the 32-bit InterBase Server ------------------------------------------------- C++Builder Enterprise and Client/Server contains the 32-bit five- user InterBase Server for Windows 95NT. Purchase of C++Builder Client/Server, however, does not include deployment or redistribution rights for any InterBase Server files. Customers who wish to deploy InterBase Server applications must separately purchase individual copies of the InterBase Server; contact Borland at 1-800-245-7367 for details. 7. Multi-tiered Distributed Application Services ------------------------------------------------ This version of the software may include the Multi-tiered Distributed Application Services Suite (MIDAS). MIDAS comprises the Business ObjectBroker, OLEnterprise, the Remote DataBroker, and the ConstraintBroker Manager (SQL Explorer). See LICENSE.TXT for specific rights and requirements for distributing the modules that comprise MIDAS, and the Client Dataset Server Deployment License. The Client Dataset Server Deployment License is not required for deploying an application in which the Client Computer and the Server Computer are the same physical machine. For more information, see Borland's World Wide Web site (http://www.borland.com/midas/) or contact your local Borland sales office. For a list of files and components in MIDAS, see http://www.borland.com/midas/papers/components.html. 8. SQL Links deployment (Enterprise and Client/server editions) --------------------------------------------------------------- When deploying an application that uses SQL Links for Interbase, you must install MSVCRT.DLL in the Windows system directory of the target machine. In addition to the SQL Links files, client/server applications require client files for interface to communication protocols such as TCP/IP. Refer to your server documentation. Redistributables for SQL Links Software --------------------------------------- Licensed, registered users of C++Builder Enterprise and Client/Server may redistribute the files listed below ("SQL Links Software Redistributables") with programs created using this product, subject to all of the terms and conditions of the Additional License Terms for Borland Database Engine. The SQL Links Software Redistributables may be redistributed only for the purpose of executing end-user SQL Links Software applications created with C++Builder Enterprise and Client/Server. Although SQL Links Software applications developed with C++Builder Enterprise and Client/Server may be redistributed to an unlimited number of servers for end-users, you may not redistribute or otherwise share the SQL Links Software with other developers for creating SQL Links Software applications. THE SQL LINK SOFTWARE REDISTRIBUTABLES CONTAINED IN THIS PRODUCT MAY NOT BE USED BY ANYONE OTHER THAN THE INDIVIDUAL WHO IS THE LICENSED USER (OR "NAMED USER", IN THE CASE OF AN ENTITY) FOR CREATING SQL LINK SOFTWARE APPLICATIONS. You may redistribute the following files in accordance with the License Statement for this product: Oracle ---------------------------------------------- SQLORA32.DLL Oracle SQL Links driver SQL_ORA.CNF Default BDE configuration file for ORA SQL Links Sybase Db-Lib ---------------------------------------------- SQLSYB32.DLL Sybase Db-Lib SQL Links driver SQL_SYB.CNF Default BDE configuration file for SYB Db-Lib SQL Links Sybase Ct-Lib ---------------------------------------------- SQLSSC32.DLL Sybase Ct-Lib SQL Links driver SQL_SSC.CNF Default BDE configuration file for SYB Ct-Lib SQL Links Microsoft SQL Server ---------------------------------------------- SQLMSS32.DLL Microsoft SQL Server SQL Links SQL_MSS.CNF Default BDE configuration file for MSS SQL Links Informix ---------------------------------------------- SQLINF32.DLL Informix SQL Links SQL_INF.CNF Default BDE configuration file for INF SQL Links DB/2 ---------------------------------------------- SQLDB232.DLL DB/2 SQL Links SQL_DB2.CNF Default BDE configuration file for DB/2 SQL Links InterBase ---------------------------------------------- SQLINT32.DLL InterBase SQL Links driver SQL_INT.CNF Default BDE configuration file for INT SQL Links For Borland Database Engine (BDE) redistributable files, see the "Borland Database Engine (BDE) Redistributable Files" section above. 9. Removed or modified "Redistributable" files ---------------------------------------------- BORLAND RESERVES THE RIGHT TO REMOVE OR MODIFY INDIVIDUAL REDISTRIBUTABLE FILES FROM THIS BORLAND SOFTWARE PRODUCT, AT ANY TIME PRIOR TO RELEASE OF THE PRODUCT, REGARDLESS OF WHETHER SUCH FILES CONTINUE TO BE LISTED AS "REDISTRIBUTABLE" UPON RELEASE OF THE PRODUCT. BORLAND SHALL HAVE NO OBLIGATION WHATSOEVER IN CONNECTION WITH ANY FILE WHICH IS LISTED AS "REDISTRIBUTABLE" BUT HAS BEEN REMOVED FROM THE PRODUCT PRIOR TO THE PRODUCT'S RELEASE. ---------------------------------------------------------------------- Unless otherwise noted, all materials provided in this release are Copyright 1983 - 1998 by Borland International. ------------------------------- END ----------------------------------